home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
pc_board
/
ulp092b.zip
/
HISTORY.TXT
< prev
next >
Wrap
Text File
|
1992-03-29
|
8KB
|
142 lines
┌───────────────────┐
│ │ ║ UpLoadProcessor Revision History File
│ ╥ ╥ ╥ │ ║
│ ║ ║ ║ ╓──╖ │ ║
│ ║ ║ ║ ║ ║ │ ║ The following is a list of the most
│ ╙───╜ ╨ ║──╜ │ ║ recent changes made to the ULP system
│ ╨ │ ║ by revision level, in reverse order.
└───────────────────┘ ║
════════════════════╝
* NOTE: I've gotten several questions regarding ARJ SFX archives and ULP's
inability to detect them. This is not a limitation of ULP, but bugs in
ARJ versions 2.21, 2.21a and 2.22. The ARJ SFX signature was not
inserted into the ARJ SFX header, therefore no program relying on this
signature (such as ULP) cannot detect ARJ SFXs created with these
versions. Version 2.20 and 2.30 correctly insert the signature.
0.92ß - ULPID.EXE has been removed from the ULP distribution archive. It
(3/29/92) will be re-released at a later date as a separate product for
non-ULP users. The original intent for ULPID is no longer necessary,
as ULPTEST performs all of the same checking ULPID did (and has for
some time); there is no need to bloat the distribution archive. If
you need to branch in PCBTEST.BAT for some reason, use PCBoard's
TESTFILE.EXE utility.
CONFIGURATION FILE CHANGE!!! ULPTEST is now capable of generating
status information for the user online through the COM port. The COM
port information can be added on the command line, or read from
PCBOARD.DAT and PCBOARD.SYS, defined either from the command line or
the PCBoard environment variables. Refer to the COMM_IO parameter in
the configuration file and documentation. Note: the comm I/O
routines I am currently using support only IRQ2-7; this should
support most systems. If you require a high interrupt, please
contact me.
CONFIGURATION FILE CHANGE!!! The maximum number of lines to be
inserted from an internal description is now configurable. CDC has
defined that the maximum number of lines for FILE_ID.DIZ is 10; ULP
previously had no limit (this probably wasn't wise). Refer to the
DESC_LIMIT parameter in the configuration file and documentation.
CONFIGURATION FILE CHANGE!!! ULP and ULPTEST can now validate the
CRC database before using it, to ensure that they are not using a
corrupted database. This was installed for users who may be nervous
about the validity of their database; I want to emphasize that there
have been NO reports of corrupted databases to date. Note that this
only validates the CRC for the period of time since the last
database compile (-S option). Make backups of your database
frequently, as nothing can be done to recover a corrupted database.
Refer to the DB_VALIDATE configuration option in the documentation.
The node number parameter is now optional in ULPTEST. ULPTEST will
attempt to obtain the node number from PCBOARD.SYS, the path to
which is either defined on the command-line or from the PCBoard
environment variables. If you have the environment variables
disabled (using the /NOENV switch in PCBoard), you will have to
create a separate PCBTEST.BAT for each node with the specified node
number on the command line. Refer to the documentation for a
complete explanation.
The command line switches have been changed for the ULP system
programs. All switches now have '-' identifiers so that arguments
can be included in any order, and to support wildcards in the future
(I hope). Refer to the documentation for more information.
A function has been added to ULPDB to review an archive and report
which files inside the archive are already in the database. This
feature can be used to help determine if an archive rejected for
duplication should be accepted.
CONFIGURATION FILE CHANGE!!! An ASCII text file viewing utility
(such as Vernon Buerg's LIST) is required for the new ULPDB viewing
function. Refer to the VIEWER configuration parameter in the
documentation.
With the addition of COM I/O to ULPTEST, all VERIFY.ULP files
uploaded to pre-verify archives are now failed by ULPTEST to prevent
the user from getting upload credit for uploading a VERIFY.ULP file
(for those boards enforcing download ratios).
Hey! Check it out! No bugs reported or found in the last version...
0.91ß - The first beta test release (finally!); all major features have been
(3/2/92) installed, and only bug fixes and minor improvements will occur
before release of version 1.00. The beta releases are planned to be
less frequent than the alpha releases were, probably on the order of
every 4 weeks or so.
CONFIGURATION FILE CHANGE!!! The CRC duplicate database format has
been changed, resulting in a 50% increase of the main database size.
The .NEW database file has been obsoleted; remove this parameter
from your configuration files. This change was required to provide
room to add features now and in the future. A utility is included
(DBCVT.EXE) that will convert your current database to the new
format. Just run DBCVT from your ULP directory and answer the
questions.
CONFIGURATION FILE CHANGE!!! ULP and ULPTEST now support two logging
modes: verbose and terse, set by the parameter LOG_MODE. The terse
mode is equivalent to the original logging, while the verbose mode
includes more information about the archive compiled during testing.
ULPTEST now updates the duplicate database with its own data to
prevent a user from uploading the same file twice. Prior to this
release, the database was updated only during the event by ULP,
allowing this potential problem. Since ULPTEST does not perform as
stringent of tests as ULP does, it's CRC data is discarded by ULPDB
during compilation. Therefore, you must run ULP in your event at
least as often as you run ULPDB to compile your database, to ensure
that the data is entered permanently into the CRC database.
ULPADS no longer requires the configuration file as a parameter;
instead you supply the name of the BBS ads database file. This
resulted in a reduction of the program size (about 5K).
PCBTEST.BAT FILE CHANGE!!! ULPTEST would fail archives for
duplication and/or age limits when invoked using PCBoard's TEST
function. This has been fixed, and the %2 parameter passed to
PCBTEST.BAT by PCBoard must be passed to ULPTEST as well. Refer to
the new PCBTEST.BAT file included in this archive.
ULPTEST would log a negative age to the log file for an archive that
failed the age limit. The archive was correctly processed and
dispositioned; just the logging was incorrect. ULPTEST could leave
its temporary subdirectory behind with a read-only archive in it
under special circumstances with nested archives. And (barf!)
ULPTEST could hang the system if an invalid VERIFY.ULP file was
uploaded for upload preverification. All are fixed (*sigh*).
If an ARC, PAK or ZIP archive was hacked up bad enough, ULP and
ULPTEST would hang during file screening, usually causing a memory
error. The archive screening routine has been strengthened handle
badly hacked archives.
Worked on the documentation some more to help clarify the operation
and installation of ULP. Hopefully it won't stink (as bad) now...
0.90α/A through 0.90α/I - Alpha test versions...